Powertag: manufacturing and support system method and apparatus for multi-computer solutions

ABSTRACT

A solutions-based computer system manufacturing process includes assembling computer and storage system components for creation of a given solution-based product as a function of a customer order or plan. The process further includes assigning a solution identifier to the solution-based product. The solution identifier includes a solution type and a unique identifier within the solution type.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to and is a divisional of co-ownedco-pending U.S. patent application Ser. No. 09/916,596, filed Jul. 27,2001, which is incorporated herein by reference in its entirety.

BACKGROUND

This disclosure generally relates to computer system manufacturing andservice, and more particularly, to supporting solutions-based systemapparatus and methods. A method is needed to service a built-to-ordergroup of distinct computer systems that the customer intends tointerconnect in a way that makes them a “solution”.

Computer system manufacturers face major challenges with on-linesupport, phone-based technical support, on-site service, and the upgradeprocesses for solutions-based products such as Storage Area Networks(SANs), Network Attached Storage (NAS), server clusters, and morerecently, e-commerce configurations consisting of multiple servers,storage systems, software components, and networking interconnects.Historically focused on “boxed systems”, a build-to-order computermanufacturer assigns “Service Tags” to individual computer systemswhether they are used as individual systems or as part of a largersystem of components to provide a solution. While this approach isadequate to service and upgrade a single monolithic box (the box), itfails to work when that box is an integral part of a larger solutionwith complex interdependencies.

On-Line Support:

As a build-to-order computer manufacturer's computing solutions becomeincreasingly complex, the ability to post product and educationaldocumentation, technical alerts, and software updates online will be acritical requirement for success in the respective market space. Forexample, the prompt availability and accessibility of a single softwaredriver update may be needed to solve a critical problem in a largesolution such as a Storage Area Network or Server Cluster. Using just aservice tag, there is no way to associate the needs of the solution withthe needs of the specific box. The ability to post product andeducational documentation, technical alerts, and software updates forthe solution online will also be a major challenge with respect toStorage Domain Management (SDM) and storage virtualization products.

With conventional on-line support systems, customers and computermanufacturer support personnel access updates and information viamechanisms such as on-line support systems and various search tools.Further, with conventional on-line support systems, documentation, OEMrecommendations, and knowledge base searches are provided via theservice tag. Providing information to the customer using a singlemachine's service tag cannot account for the complexities ofinterconnecting that device with other devices and software indistributed environments. The conventional on-line support systempossesses no capability to correlate multiple systems and softwarecomponents involved in solving a complex problem. For example, if agiven configuration comprises a server cluster using Microsoft's ClusterServer software, then the configuration includes the exact server modelsthe customer is using, the shared storage enclosure(s), the operatingsystem, the clustering software, and any other system components such ascluster-enabled RAID controllers. These components have individualsupport characteristics associated with them, but there is also asuperset of support required for the implementation as a whole and thesoftware components. This superset of support might include certaindiagnostics routines to trouble-shoot any problems in the solution,validation routines to check for correct installation and wiring of theboxes in the solution, capture and audit mechanisms for reporting assetinformation for the entire solution, monitoring routines for sendinghealth information to the support lines via the Internet, and the like.

Conventionally, none of the above identified configuration items aretied together when on-line support offerings and resources are presentedin response to an on-line support inquiry. As a result, the supportgiven might not be relevant to the particular configuration. Forexample, a customer may require a software update specific to a certaincluster configuration. The particular customer may be unable to locatethe desired software update file because the conventional system lackscapability to search for updates based on the cluster configuration.

Tech Support:

The “Service Tag-centric” approach to support causes errors in TechnicalSupport organizations and hinders the computer manufacturer's ability todeliver effective support to high-end computing solutions. Thetechnician's access to internal support resources is similarly orientedto the “box” rather than the “solution”. The complex interdependencieswithin the high-end computing and enterprise solutions are constantlychanging. The complex interdependencies are also too numerous fortechnicians to memorize. Accordingly, it would be desirable for on-linesystem support tools to have an ability to present solution-orientedinformation to technicians for assisting technicians in their support ofthese enterprise solutions.

On Site Service:

If a technical support representative decides that a given server orstorage device requires service, then the representative may dispatchon-site service to fix the server. The dispatch may include, forexample, dispatching a technician who is trained in break/fix tacticsfor a specific component or all the specific components inside a single“box”. For instance, the technician may be perfectly capable ofreplacing a Fibre Channel host bus adapter (HBA) in a particular server,but may not understand actions required to recover proper operationsthroughout the solution once the HBA is replaced. It is becoming farmore commonplace for that HBA to be plugged into a Fibre Channel switchwith complex Fibre Channel zoning definitions that need to be modifiedor reconfigured if and when that HBA is replaced.

Upgrades:

Adding components and/or software upgrades for a given solution can bevery complicated. For instance, significant “missing and wrong” andexcessive field rework can be created because the sales and technicalsupport representatives have a service tag focus. Accordingly, the salesand technical support representative are unable to efficiently viewupgrade requirements based on the entire solution's configuration.

For example, a customer may desire to purchase an additional server orstorage nodes or additional infrastructure for their Storage AreaNetwork (SAN). For that customer, the following must first bedetermined: the overall topology and size of the SAN, as well as thenumber of servers and storage in the customer's SAN, what versions offirmware, PROM, device drivers, storage software, etc. are in placebefore determining the scope of work required, as well as productsneeded, to upgrade the solution. The process of manually identifying theinstalled the components and configuration can be very time consuming,as well as prone to error.

Accordingly, it would be desirable to provide a support system having anability to present solution-oriented information for assisting in thesupport of enterprise solutions and other large solutions with complexinterdependencies.

SUMMARY

A solutions-based computer system manufacturing process includesassembling computer and storage system components for creation of agiven solution-based product as a function of a customer order or plan.The process further includes assigning a solution identifier to thesolution-based product. The solution identifier includes a solution typeand a unique identifier within the solution type.

The embodiments of the present disclosures provide the technicaladvantage of enabling the presentation of solution-oriented informationas a function of a unique solution identifier for assisting in thesupport of enterprise solutions and other large solutions with complexinterdependencies.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram view of an example computer systemsolutions-based product manufactured according to one embodiment of thepresent disclosure.

FIG. 2 is a block diagram view of an example storage systemsolutions-based product manufactured according to another embodiment ofthe present disclosure.

FIG. 3 is a block diagram view of a solutions-based product includingservers and storage systems according to another embodiment of thepresent disclosure.

FIG. 4 is a flow diagram view of the PowerTag method and system inaccordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

In FIG. 1, a system block diagram of a solutions-based computer system10 is illustrated having features thereof configured in accordance witha custom configured computer system order or plan in a build to ordermanufacturing environment. The computer system 10 includes at least onecentral processing unit (CPU) (12, 14), memory 16, input/output (I/O)devices, such as a display, a keyboard, a mouse, and associatedcontrollers, collectively designated by a reference numeral 18, a harddisk drive 20, and other storage devices and/or controllers, such as mayinclude a floppy disk drive, a CD-ROM drive, and the like, collectivelydesignated by a reference numeral 22, and various other subsystems, suchas a network interface card, collectively designated by a referencenumeral 24, all interconnected via one or more buses. One or morecomputer-readable media, such as a floppy disk, CD-ROM, or the like, mayalso be included. Computer system 10 further includes at least one ormore operating system 26 and at least one or more software applications28.

In FIG. 2, a system block diagram of a solution-based storage system 30is illustrated having features thereof configured in accordance with acustom configured storage system order or plan in a build-to-ordermanufacturing environment. The storage system 30 includes at least oneor more storage controllers (32,34) and at least one or more disks(36,38,40,42,44). Storage system 30 further includes firmware 46 andsoftware 48.

In FIG. 3, a system block diagram of a solutions-based product 50 isillustrated. The solutions-based product 50 includes at least one ormore servers (52,54) and at least one or more storage systems 56according to another embodiment of the present disclosure. The varioussystems (52,54,56) are interconnected and/or coupled together accordingto the particular requirements of the solutions-based product,collectively represented by reference numeral 58. The PowerTagidentifier, as discussed further herein, tracks a number of thesedevices that compose a given solution.

In a build-to-order solutions-based computer system manufacturingenvironment, hardware components are installed into at least one or moretarget computer and/or storage systems to be included within a givensolutions-based product. The particular hardware components are per acustom order or plan for a given solutions-based product. Predeterminedfiles are downloaded onto the hard drive or storage devices of thetarget system(s) of the particular solutions-based product. Thepredetermined files are per the custom order or plan, also. The one ormore computer and/or storage system is then paired with other systems,such as other computers, storage devices, and/or network equipmentmaking up the solutions-based product. Software is added to theindividual computer and/or storage systems to enable them to functiontogether in a pre-defined way. The process may further include testingof the solutions-based product prior to shipment to a customer.

The solutions-based computer system 10 of FIG. 1 may also represent aPowerTag system for carrying out the PowerTag method as discussedherein. In addition, the PowerTag method of the present embodiments asdescribed herein can be implemented in software, using programmingtechniques known in the art. The software may further be stored onsuitable computer-readable media and/or transmitted via a network, suchas, a global computer network or other suitable network.

According to one embodiment of the present disclosure, “PowerTag”includes a logical entity for capturing a specific customer solution.The PowerTag system enables an identification of information for thedevices and systems comprising a given solution, as well as serviceofferings and entitlements. The PowerTag system assigns a uniquePowerTag identifier, also referred to herein as a solutions identifier,to the devices and systems comprising the given solution product. Aconfiguration of systems and software linked to a PowerTag identifiermay also be updated to reflect a customer's changing installed solution.Additionally, a customer may possess multiple PowerTag identifiers thatdefine multiple installed solutions, respectively.

In accordance with one embodiment, the PowerTag method and systemutilizes a “Relational” database model for describing the PowerTag. Inthe relational terminology, a database is represented by a table. Anentry in the database is a row in that table. Each row is made up of anumber of fields. Lastly, an index into a database is the relation'sprimary key.

According to one illustrative embodiment, the notion of a PowerTagapplies to multiple complex solutions. Some examples of what a solutionssystem manufacturer provides in this space may include Microsoft ClusterServer (MSCS), Microsoft and MSCS are trademarks of MicrosoftCorporation, High Performance Computing clusters (HPCC), and SAN.

According to one embodiment, the PowerTag includes, at a minimum, twofields for describing the PowerTag. The fields include: 1) type, and 2)unique identifier. Accordingly, each PowerTag includes a concatenationof these two fields as follows:

-   -   |Type| |Unique identifier|

Consider the following example. To begin, mappings are assigned for theabove-mentioned solutions of MSCS, HPCC, and SAN into prescribed types:

Solution Type MSCS: 1 HPCC: 2 SAN: 3

In addition to the above, further assume that a numbering scheme foreach identifier of a particular type starts at 000000, and that the veryfirst deployment would be 000001. Accordingly, the PowerTag for the veryfirst MSCS deployment is |1| |000001|.

In one embodiment, the PowerTag identifiers are maintained in a PowerTagtable, similar to that of the following table:

Type Unique Identifier Description 1 000001 MSCS 1 000002 MSCS 2 000001HPCC 3 000001 SAN . . . . . . . . .

In use, the sales, services and support, manufacturing, and othersimilar organizations of a solutions system manufacturer correlates eachunique PowerTag identifier to its corresponding individual components,using suitable techniques. For instance, an MSCS cluster conventionallyincludes two servers (e.g., Server A and Server B) and a storage device.In keeping with the above example, the following service tags might beassigned for the hardware components of the MSCS cluster:

-   -   MSCS Cluster    -   Server A, with service tag ABCD,    -   Server B, with service tag EFGH, and    -   Storage device, with service tag IJKL.

In addition, the PowerTag method and system may further include asuitable mechanism to define other attributes and components that maynot necessarily be designated with a service tag. For example,components, such as additional software, configuration and diagnosticutilities, and/or systems management software, may not be designatedwith a service tag. However, such items may be required to implement thesolution in the field, wherein revision control, as well as visibilityto revisions shipped, is vital to the support of the solution. In oneembodiment, a description field in a PowerTag table captures suchinformation particular to a given solution, but for which there existsno service tag. Accordingly, the list of one or more components within agiven solution may include these items, as well as the devices bearing aservice tag.

Prior to PowerTag, there was no automated way of tying together theservice tags above into their representative solution, nor was itpossible to record details about the solution itself. With the PowerTagmethod and system of the present disclosure, the solution identifier ofthe above-mentioned example would be used for indexing into the PowerTagtable that contains all MSCS deployments, with their respective servicetags listed. The PowerTag table can also include additional informationfor capturing the solution systems architecture, design, proof ofconcept, testing, and deployment of the solution. Accordingly, thePowerTag table enables the solution system manufacturer to provideupgrades, parts, technical support, installation services, etc. to agiven customer with improved confidence that an appropriate action canbe taken the first time.

In the above example, the PowerTag identifier includes |1| |000001|. Thesecond field from the PowerTag identifier provides an index into an MSCStable. An example solution type table for the solution type MSCSfollows:

Solution ID Server A Server B Storage Description 000001 ABCD EFGH IJKLDesigned by Dell Technical Consulting Deployed on Jan. 1, 2001 by CDTRevision of MSCS: 1.0 000002 QWRQ LKMV OAFP Designed by customerServiced on Jan. 14, 2001 by Wang . . . . . . . . . . . . . . .

Similarly, the method and system of the present disclosure provides theHPCC, SAN, and other solutions with their own separate tables forcapturing the service tags of their respective components, as well asother relevant information, for example, in the description field of arespective solution table.

According to one embodiment, the PowerTag system implements and deploysPowerTag identifiers on a global computer network, such as the Internet,intranet, or other network. In the embodiment, in response to solutionobject input information, the PowerTag system associates various servicetags and other solution objects into a defined solution. Accordingly,the resulting PowerTag solution object possesses attributes to enableefficient viewing and downloading of related documentation,alerts/bulletins, software updates.

According to one embodiment, regardless of whether a PowerTag isconstructed during an order entry process, or at a later point in time,for example, by a customer or service representative (e.g., over theInternet or through other means), PowerTags are maintained centrally andused by services, sales, manufacturing, engineering, and other groups,as described herein.

FIG. 4 illustrates one implementation 60 of the PowerTag method throughon-line web forms. With respect to this embodiment of the PowerTagmethod, either a customer or a solution system manufacturerrepresentative enters the service tags and select solution components ofa respective system solution for use in obtaining a PowerTag identifier,further in connection with obtaining custom support services via thePowerTag method and system.

In connection with the web forms implementation of FIG. 4, for a givensolutions-based product, in step 62, a customer enters service tags foreach component of the customer's solutions-based product, whetherhardware and/or software. The entry of the service tags may beaccomplished, for example, via a suitable entry form on a web pagehosted by the PowerTag system for implementing the PowerTag method.

Responsive to a completion of entering of service tags for a givensolutions-based product, the PowerTag system generates a unique PowerTagidentifier in step 64. Generation of the PowerTag identifier is inaccordance with that as discussed further herein.

In step 66, a customer and/or service representative enters a PowerTagidentifier for a solution-based system. Responsive to entry of thePowerTag identifier, in step 68, the PowerTag system provides custom websupport services. For example, the PowerTag system dynamically generatesweb pages particular to the specific solution-based system. The PowerTagsystem constructs the dynamically generated web pages using informationobtained from one or more of a documentation system 70, a file librarysystem 72, and a knowledgebase system 74, as a function of the PowerTagidentifier. The particular web page is further a function of the type ofservice (e.g., sales, on-line support, on-line documentation,phone-based tech support, on site service, upgrade, entitlement, orother similar type service) being requested by the customer and/orcustomer service representative, further as discussed herein. Inaddition, each of the documentation system 70, the file library system72, and the knowledge base system 74 includes one or more server system,storage system, management system, and corresponding software for therespective system.

The PowerTag solution object may also be the object of an entitlementsuch as with respect to a “Platinum” or “Gold” service offering.Accordingly, the PowerTag solution object enables rendering ofsignificant improvements in sales and technical support, as well asfield-based installations, repairs and upgrades.

According to another embodiment, the PowerTag system includes a factoryintegrated system for generating PowerTag solution objects as part ofthe manufacturing process. For example, in the factory integratedPowerTag system, multiple systems and software components are linkedinto a defined solution for the customer, along with the services soldin support of the solution.

In another embodiment, the PowerTag system applies to computer systemvendors. A computer vendor may implement PowerTag using informationsystems and a direct model. In one example, the direct model relates toa build-to-order computer system manufacturing process.

According to another illustrative embodiment, PowerTag components caninclude a multitude of various components. For example, the PowerTagcomponents may include one or more of the following:

-   -   Servers: each model and the associated service tags, operating        system (O/S), basic input output system (BIOS), peripherals and        respective drivers, etc.    -   Storage components: each model and the associated service tags,        firmware, programmable read only memory (PROM) revision, etc.    -   Software: clustering software, backup software, storage        consolidation software, storage management and configuration        software, factory installed applications, on-site installation        of software or applications, etc.    -   Service offerings: service offerings can include standard (std)        availability guarantee, twenty-four hours per day seven days a        week (24×7) availability guarantee, “Gold”, “Platinum”, etc.    -   On-Site Installation choices: specific to a given solution,        there may be installation options that can be automatically        planned and coordinated using the solution identifier for the        system. For instance, a first service provider comes in for        physical wiring of the components, and a second provider comes        in to configure software. This coordination can be accomplished        by knowing the type of the solution and its specific        installation options.    -   Links to entitlement: statements of work (SOW's), product        documentation, software updates, technical bulletins, etc., as        they relate to a given solution and it's components.        Sales:

With respect to a computer manufacturer's PowerTag offering, inaccordance with an illustrative embodiment of the present disclosure,the computer manufacturer's customers would have additional incentivefor purchasing most, if not all, software components with their hardwarefrom the same computer manufacturer. Hardware and software components ofa given system solution of configuration would be tied together via aPowerTag identifier. Accordingly, a hardware company could implementsupport and service for the customer's entire configuration; as opposedto providing support and service just for the hardware components withredirectors to software companies for everything else.

On-Line Support:

With respect to an on-line support web site utilizing the PowerTagsystem in accordance with the present embodiments, a PowerTag supportmethod may be carried out as follows. A customer or servicerepresentative accessing the on-line support enters a PowerTagidentifier on the support web site when prompted for the PowerTag. Inone embodiment, if the customer or service representative enters aService Tag instead of the PowerTag, then the PowerTag system performs asearch for the appropriate PowerTag identifier within the system, usingsuitable search techniques. The support web site may include, forexample, http://www.support.dell.com, a premier support page, or othersupport web site.

In response to the entered PowerTag identifier, the PowerTag systemoutputs information specific to the solution. The solution may include,for example, Fibre Channel, SAN configuration, etc. Accordingly, thecustomer receives information that is specific to the particularsolution. The solution specific information can include one or more ofdetails on component configuration, possible upgrades for BIOS, drivers,firmware, SAN software, etc. In addition, Knowledge Base and FileLibrary systems can be tied in to a solution. Accordingly, the method ofimplementing an on-line support web site utilizing the PowerTag systemand method could include categorizing Knowledge Base and All Files bySystem results by component, that is, server, storage, cluster software,SAN configuration, etc.

On-Line Documentation:

According to one embodiment, the PowerTag system dynamically constructsan on-line documentation page for a given solution system. For example,a particular on-line documentation page may include at least one or moreof server guides, storage guides, a management software guide, clusterguide, SAN guide, etc. The PowerTag system customizes the particularon-line documentation page based upon a customer's installation, furtheras a function of a corresponding PowerTag identifier.

Phone-Based Tech Support:

The PowerTag method and system apparatus of the present embodimentsenable support entities, such as regional expertise centers, forsupporting “Platinum” and “Gold” customers, to provide precise andaccurate support for complex enterprise solutions. In response to aninput of a service tag or PowerTag identifier, the PowerTag systemgenerates information pertaining to the customer's particular solutionsystem. In one embodiment, the PowerTag system further provides adisplay of the customer's solution and renders the solution visible tothe support technician or support team. Accordingly, whether thecustomer provides a service tag or PowerTag to the support technician,the customer's solution will be immediately visible to the support team.If a support technician receives a service tag that belongs to asolution or the solution ID of a SAN, for example, then the supporttechnician routes the call to a technician trained on Fibre ChannelSANs. Equipped with the customer's particular solution, the SAN-trainedtechnician will then have all the necessary information and tools toboth diagnose component issues and system issues.

The PowerTag method and system apparatus further provide the advantageof making it easier to troubleshoot a solution. For example, thesolution ID would not cover components that a customer may have added tothe customer's system solution independent of the original solutionsystem manufacturer. The original solution system manufacture mayinclude, for example, the build-to-order computer system manufacturer.In addition, a customer may have installed an additional SAN-attachednode or cluster node not manufacturer-installed. Tracking foreignobjects and their respective behavior assists in diagnosis of a problem.Tracking of foreign objects also illuminates potential issues that thecustomer may not have been aware of when the customer added theadditional components.

On Site Service:

A technical support unit of the computer manufacturer may decide that aserver needs service and, in response, dispatches on-site service to fixthe server. With the use of the PowerTag method and system of thepresent disclosure, the appropriate information and personnel can besent to repair and/or fix the issue. For example, if the fix is afirmware update, then the service technician could be sent to thecustomer site with the service tags of other systems of the customerthat must have their firmware upgraded as part of the fix. This“collective upgrade” is needed because many times for upgrading asolution, multiple components within it have to be upgraded, and notjust a single component. In addition, when on-site service is dispatchedto repair a device within a solution, the servicing party is able toprovide the correct skills and tools necessary for the repair actionwhen the PowerTag identifies the entire solution within which the deviceresides. Such on-site service facilitated via the PowerTag method andsystem could also be useful for providing service on system solutionshaving a high availability service offering and guarantee.

Upgrades:

With additional information regarding a particular system solutionobtained via use of the PowerTag method and system of the presentdisclosure, upgrades can be handled more smoothly. For example, if acustomer has a four node SAN and wants to add two nodes, then what wouldthe customer need in particular for adding the additional two nodes? Thecustomer might need just two more nodes or the customer might need toupgrade storage software or switch firmware to a new version supportingmore nodes (requiring on-site service), etc. The PowerTag method andsystem facilitates easy accessibility to the necessary information.

According to one embodiment, the PowerTag method and system performassignment of the Solution IDs implemented via on-line web resources, aswell as in an order-entry system for Enterprise-class products. Forinstance, the order-entry system may be applicable for the ordering ofcomplete cluster systems, storage area networks (SANs), and NAS asstorage products. Implementing the PowerTag methodology in this mannerwill enable the solution system manufacturer to take service and supportto a higher level for “productized solutions” that have varyingcomponents. The PowerTag method and system may be implemented directlyinto a business model for doing business over the Internet and directwith customers.

Training:

According to another embodiment, web-based training for complexsolutions such as NAS, SAN, Storage Domain Management (SDM), and clustersystems are linked to PowerTags. For example, if a customer seekssupport for a server that is part of a SAN PowerTag, then in response toreceipt of the SAN PowerTag identifier, the PowerTag system provides thecustomer with access to links for web-based SAN training.

Accordingly, the PowerTag solutions-based manufacturing and supportsystem method and apparatus advantageously leverages a direct model tosupport system-based configurations, like SAN, clusters, NAS, and othersolution stacks.

Although only a few exemplary embodiments have been described in detailabove, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theforegoing disclosure. Accordingly, all such modifications are intendedto be included within the scope of these embodiments as defined in thefollowing claims. In the claims, means-plus-function clauses areintended to cover the structures described herein as performing therecited function and not only structural equivalents, but alsoequivalent structures.

1. A method of supporting a plurality of interconnected computersystems, comprising: providing a solution that includes a plurality ofcomputer systems that are operable to be interconnected in order tofunction together in a predefined manner, wherein each of the pluralityof computer systems includes a service tag that identifies a pluralityof hardware components in that computer system; assigning a solution tagto the solution, wherein the solution tag is associated with each of theservice tags and includes information about a plurality of softwarecomponents used with the solution that allow the solution to functiontogether in the predefined manner; receiving the solution tag; using thesolutions tag to retrieve solution specific hardware information relatedto at least one of the plurality of hardware components in at least oneof the plurality of computer systems and solution specific softwareinformation related to at least one of the plurality of softwarecomponents used with the solution; and generating a web page includingthe solution specific hardware information and the solution specificsoftware information.
 2. The method of claim 1, wherein the plurality ofcomputer systems includes a server.
 3. The method of claim 1, whereinthe plurality of computer systems includes a storage system.
 4. Themethod of claim 1, wherein the plurality of software components usedwith the solution includes system management software, configurationutilities, and diagnostic utilities.
 5. The method of claim 1, furthercomprising: storing the solution tag and the associated service tags andsoftware information in a database.
 6. The method of claim 1, furthercomprising: receiving, over a network, the service tag for each of theplurality of computer systems.
 7. The method of claim 1, furthercomprising: updating the solution tag to reflect an updated computersystem in the solution.
 8. The method of claim 1, further comprising;updating the solution tag to reflect an updated software component usedwith the solution.
 9. A manufacturing system comprising: a processor; astorage accessible by the processor, the storage including program codeprocessible by the processor for implementing a computer systemmanufacturing process, the manufacturing process including assembling asolution that includes a plurality of computer systems that are operableto be interconnected in order to function together in a predefinedmanner, assigning a service tag to each of the plurality of computersystems that identifies a plurality of hardware components in thatcomputer system, assigning a solution tag to the solution, wherein thesolution tag is associated with each of the service tags and includesinformation about a plurality of software components used with thesolution that allow the solution to function together in the predefinedmanner; a database coupled to the processor for storing the solution tagand the associated service tags and software information; a networkinterface coupled to the processor for receiving the solution tag over anetwork; a retriever coupled to the processor for retrieving solutionspecific hardware information related to at least one of the pluralityof hardware components in at least one of the plurality of computersystems and solution specific software information related to at leastone of the plurality of software components used with the solution; anda web page generator coupled to the processor for generating a web pageincluding the solution specific hardware information and the solutionspecific software information and providing the web page over thenetwork.
 10. The computer system of claim 9, wherein the plurality ofcomputer systems include a server.
 11. The computer system of claim 9,wherein the plurality of computer systems include a storage system. 12.The computer system of claim 9, wherein the plurality of softwarecomponents used with the solution include system management software,configuration utilities, and diagnostic utilities.
 13. The computersystem of claim 9, further comprising: an updater coupled to theprocessor for updating the solution tag to reflect an updated computersystem in the solution.
 14. The computer system of claim 9, furthercomprising: an updater coupled to the processor for updating thesolution tag to reflect an updated software component used with thesolution.